-
Notifications
You must be signed in to change notification settings - Fork 332
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEAT]: Add trustchain & createQRCodeHostInstance flow #7520
Conversation
The latest updates on your projects. Learn more about Vercel for Git βοΈ 5 Skipped Deployments
|
81b473e
to
b08f703
Compare
.../ledger-live-mobile/src/newArch/features/Accounts/screens/AddAccount/components/StepFlow.tsx
Outdated
Show resolved
Hide resolved
.../ledger-live-mobile/src/newArch/features/Accounts/screens/AddAccount/components/StepFlow.tsx
Show resolved
Hide resolved
}, | ||
onDisplayDigits: digits => { | ||
dispatch(setQrCodePinCode(digits)); | ||
dispatch(setFlow({ flow: Flow.Synchronize, step: Step.PinCode })); | ||
}, | ||
addMember: async member => { | ||
await sdk.addMember(trustchain, memberCredentials, member); | ||
hasCompleted = true; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you should prefer to do this after createQRCodeHostInstance
's Promise terminates.
NB: it can also fails, so maybe you can .then( successHandling, errorHandling )
on it (depending if you need to handle the error or not, for instance the websocket can be closed due to network cut )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, i actually misunderstood the code.
I see that you use the hasCompleted in a laterthen
, is it because the catch
sometimes recover from an error? in that case maybe the then() should be moved before?
actually you have guarantee that if promise succeed, it means the whole process was successful π€
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can try opening the QRCode screen on LLD, for example, and do nothing. After a while, you'll see the success screen appear, which means you're in the then
1a0e61b
to
d1686a7
Compare
apps/ledger-live-mobile/src/newArch/features/WalletSync/__integrations__/shared.tsx
Outdated
Show resolved
Hide resolved
[FIX]: issue when staying long time on DisplayQRcode page Rework Hook
d1686a7
to
e1bdf18
Compare
β Checklist
npx changeset
was attached.π Description
β Context
π§ Checklist for the PR Reviewers